I'm sorry. I did NOT write BSD
It's about convergence through global solutions
You build it, you run it
Nothing new in the horizon probably for you * first mention in 2006, by Werner Vogels / Amazon * Nice elaboration behind the rationale here
That means there's no ops/support/systems/devops team.
{
"format": "webp",
"watermark": {
"location": "north",
"margin": "20px",
"dimension": "20%"
},
"actions": [
{
"resize": {
"width": 300,
"fit": {
"type": "clip"
}
}
}
],
"quality": 90
}Lots of (user) contents given the classified business. Sites are dynamic by nature. Some of them do adapt the request to the device. Blocking redesigns or improvements because lack of capacity to reprocess
CDNs able to transform contents: * *?
SaaS solutions: * imgix * libpixel * Cloudinary
(Almost) No incidents. We would be able to maintain this with a single engineer
But be careful: if you invest 0 efforts, you kill a service * Stops being competitive * Starts being legacy * Starts to disconnect from current needs
So we try to convince the company it requires, at least, the focus of two engineers.
No space for "one time" actions.
And capacity to incorporate everything to the pipeline
Yeah, Google and error budgets...
... but helped us to understand, tune, and get the trust from Sch sites, avoiding major disruptions when major onboardings
We may.
And it may be a good moment to consider opencensus.
Some major Marketplaces are not using the service, yet
Hoverfly: similar in concept to the Simian Army from Netflix, but specialized in API degradations
Sch*
Edge colleagues